Repository navigation
Conversation
|
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Allow CRLF as well as LF after fenced-code language headers in
MultiCodeBlockParserandDescriptiveCodeBlockParser. Previously ajson\r\nheader was retained as content, causingJSONParserto reject an otherwise valid fenced JSON response. The descriptive parser could likewise putpythoninto generated source files.Only the header line-ending match changes; line endings within the extracted content are preserved.
Verification
python -m pytest tests/llm/test_parser.py --no-cov -o addopts='' -ra: 45 passed (existing Pydantic deprecation warnings).git diff --checkpassed for both changed files.No provider calls or full application suite were run.
Prepared with AI assistance; the checks above were run locally.